Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.x] build(deps): bump go.opentelemetry.io/collector/pdata from 1.21.0 to 1.22.0 in the otel group (backport #14986) #15014

Merged
merged 4 commits into from
Dec 20, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Dec 20, 2024

Bumps the otel group with 1 update: go.opentelemetry.io/collector/pdata.

Updates go.opentelemetry.io/collector/pdata from 1.21.0 to 1.22.0

Release notes

Sourced from go.opentelemetry.io/collector/pdata's releases.

v1.17.0/v0.111.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.111.0

🆕 The binary release adds a new OTLP-only distro. Feel free to leave us feedback on this new distro on the opentelemetry-collector-releases issue tracker.

End User Changelog

🐛 Known bugs 🐛

  • The ocb binary has an identified bug caused by the fact that some of the providers have been marked stable and the default providers in the ocb binary still use the unstable version. In order to fix this explicitly add the default providers in your otel builder config, if not already configured:
providers:
  - gomod: go.opentelemetry.io/collector/confmap/provider/envprovider v1.17.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/fileprovider v1.17.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/httpprovider v1.17.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/httpsprovider v1.17.0
  - gomod: go.opentelemetry.io/collector/confmap/provider/yamlprovider v1.17.0

This release removes the logging exporter. See #11337 to migrate to the debug exporter.

🛑 Breaking changes 🛑

  • service/telemetry: Change default metrics address to "localhost:8888" instead of ":8888" (#11251) This behavior can be disabled by disabling the feature gate telemetry.UseLocalHostAsDefaultMetricsAddress.
  • loggingexporter: Removed the deprecated logging exporter. Use the debug exporter instead. (#11037). You can read issue #11337 for migration instructions.

🚩 Deprecations 🚩

  • service/telemetry: Deprecate service::telemetry::metrics::address in favor of service::telemetry::metrics::readers. (#11205)
  • processorhelper: Deprecate BuildProcessorMetricName as it's no longer needed since introduction of mdatagen (#11302)

💡 Enhancements 💡

  • ocb: create docker images for OCB, per open-telemetry/opentelemetry-collector-releases#671 (#5712) Adds standard Docker images for OCB to Dockerhub and GitHub, see hub.docker.com/r/otel/opentelemetry-collector-builder
  • confighttp: Snappy compression to lazy read for memory efficiency (#11177)
  • httpsprovider: Mark the httpsprovider as stable. (#11191)
  • httpprovider: Mark the httpprovider as stable. (#11191)
  • yamlprovider: Mark the yamlprovider as stable. (#11192)
  • confmap: Allow using any YAML structure as a string when loading configuration including time.Time formats (#10659) Previously, fields with time.Time formats could not be used as strings in configurations

🧰 Bug fixes 🧰

  • processorhelper: Fix data race condition, concurrent writes to the err variable, causes UB (Undefined Behavior) (#11350)
  • cmd/builder: re-adds function to properly set and view version number of OpenTelemetry Collector Builder (ocb) binaries (#11208)
  • pdata: Unmarshal Span and SpanLink flags from JSON (#11267)

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/pdata's changelog.

v1.22.0/v0.116.0

🛑 Breaking changes 🛑

  • component: Remove deprecated TelemetrySettings.LeveledMeterProvider (#11811)
  • scraperhelper: Remove deprecated scraperhelper.Scraper and helpers (#11803)

🚩 Deprecations 🚩

  • connector: Deprecate connectorprofiles module in favor of xconnector to allow adding more experimental data types. (#11778)
  • consumererror: Deprecate consumererrorprofiles module in favor of xconsumererror to allow adding more experimental data types. (#11778)
  • consumer: Deprecate consumerprofiles module in favor of xconsumer to allow adding more experimental data types. (#11778)
  • exporterhelper: Deprecate exporterhelperprofiles module in favor of xexporterhelper to allow adding more experimental data types. (#11778)
  • exporter: Deprecate exporterprofiles module in favor of xexporter to allow adding more experimental data types. (#11778)
  • pipeline: Deprecate pipelineprofiles module in favor of xpipeline to allow adding more experimental data types. (#11778)
  • processorhelper: Deprecate processorhelperprofiles module in favor of xprocessorhelper to allow adding more experimental data types. (#11778)
  • processor: Deprecate processorprofiles module in favor of xprocessor to allow adding more experimental data types. (#11778)
  • receiver: Deprecate receiverprofiles module in favor of xreceiver to allow adding more experimental data types. (#11778)
  • receiver/scrapererror: Remove the receiver/scrapererror alias. (#11003)

💡 Enhancements 💡

  • receiver/scraperhelper: Add scraper for logs (#11238)
Commits
  • 095b183 [chore] Prepare release v1.22.0/v0.116.0 (#11910)
  • 96a3ad1 [chore] put back replace and add new packages in builder yaml (#11909)
  • 6a47030 [chore][release.md] mention release blockers (#11908)
  • 00852e3 Bump golang.org/x/crypto from 0.30.0 to 0.31.0 in /internal/tools (#11903)
  • 26f0fcf [chore] [docs/component-stability.md] Document relationship between versionin...
  • 8ac40a0 Define observability requirements for stable components (#11772)
  • cef6ce5 [chore] Update versions of the new experimental modules (#11897)
  • 6147243 [chore] Update version of all new experimental modules to latest commit (#11894)
  • 5da51fa [README] links caption (#11893)
  • e9bc4bd Deprecate connectorprofiles module in favor of xconnector (#11887)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

This is an automatic backport of pull request #14986 done by [Mergify](https://mergify.com).

…1.22.0 in the otel group (#14986)

* build(deps): bump go.opentelemetry.io/collector/pdata in the otel group

Bumps the otel group with 1 update: [go.opentelemetry.io/collector/pdata](https://github.com/open-telemetry/opentelemetry-collector).

Updates `go.opentelemetry.io/collector/pdata` from 1.21.0 to 1.22.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@pdata/v1.21.0...pdata/v1.22.0)

---
updated-dependencies:
- dependency-name: go.opentelemetry.io/collector/pdata
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: otel
...

Signed-off-by: dependabot[bot] <[email protected]>

* Update NOTICE.txt

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: kruskall <[email protected]>
(cherry picked from commit 98d405e)

# Conflicts:
#	go.mod
@mergify mergify bot requested a review from a team as a code owner December 20, 2024 16:43
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Dec 20, 2024
Copy link
Contributor Author

mergify bot commented Dec 20, 2024

Cherry-pick of 98d405e has failed:

On branch mergify/bp/8.x/pr-14986
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit 98d405e5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   NOTICE.txt
	modified:   go.sum

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@kruskall kruskall removed the conflicts There is a conflict in the backported pull request label Dec 20, 2024
Copy link
Contributor Author

mergify bot commented Dec 20, 2024

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

@mergify mergify bot merged commit 1ca393a into 8.x Dec 20, 2024
13 checks passed
@mergify mergify bot deleted the mergify/bp/8.x/pr-14986 branch December 20, 2024 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant